Zen7 Payment Agent

Created By
Zen7 Labs7 months ago
Overview

what is Zen7 Payment Agent?

Zen7 Payment Agent is the first practical implementation of DePA (Decentralized Payment Agent), pioneering the next generation of intelligent payment infrastructure. It fully implements the core functionalities of DePA and deploys innovative application cases in the agentic commerce domain.

how to use Zen7 Payment Agent?

To use Zen7 Payment Agent, set up the server using the command npx mcp-remote http://127.0.0.1:8015/sse and configure the MCP servers as per the provided configuration.

key features of Zen7 Payment Agent?

  • Automated encrypted payments between agents
  • Permissionless authorization mechanism
  • LLM-driven intent recognition and interaction
  • Multi-agent collaborative architecture
  • Support for A2A and MCP protocols
  • Custodial and non-custodial payment models
  • Multi-chain, multi-currency, multi-wallet support
  • High-frequency transactions and gasless operations
  • Passwordless authentication

use cases of Zen7 Payment Agent?

  1. Facilitating secure payments in decentralized applications (Dapps)
  2. Enabling automated transactions between AI agents
  3. Supporting multi-currency transactions in a decentralized environment

FAQ from Zen7 Payment Agent?

  • What is DePA?

DePA stands for Decentralized Payment Agent, a framework for intelligent payment solutions.

  • How does Zen7 ensure payment security?

Zen7 uses automated encrypted payments and a permissionless authorization mechanism to ensure security.

  • Can Zen7 handle multiple currencies?

Yes, Zen7 supports multi-currency transactions.

Server Config

{
  "mcpServers": {
    "Zen7-Payment-Agent": {
      "autoApprove": [],
      "disabled": false,
      "timeout": 60,
      "type": "sse",
      "url": "http://127.0.0.1:8015/sse"
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
Zen7 Labs
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago